Skip to main content

OpsAdmin Service Functions

alt_text

OpsAdmin Service Tasks​

alt_text The executed task times shown in this document are simply examples of when the service could run. Each OpsAdmin customer is different and will likely have a different configuration.

ESG Extract Import​

This is one of the most important tasks of the whole System as it generates the source of information for several critical processes in Ops Admin. OpsAdmin Service establishes a connection with ESG FTP Server and downloads several data extracts

Executed every day at 3am. 

Downloaded files: 

  • Datamart Accounts file: Includes information regarding plan, distributor, dates.

  • Datamart Customers File: Includes information regarding the customer.

  • Datamart LDC: Includes all the LDC data regarding a contract.

  • Datamart Service Agreement: All the service agreements that can be linked to a particular customer.

  • Datamart Market Detail: Mainly used to import Dropped Accounts to the system.

Check Data Mart Task​

This task is in charge of updating records from Ops Admin with information from ESG daily extracts. 

This task can be enabled or disabled from the Service Configuration file. The hour of execution can also be customized. This is a heavy task that usually takes around 5 hours to be completed. Currently disabled. Set up to be executed at 8am.

This task is composed by several small tasks. Each of them can be enabled/disabled independently from each other:

  • LDC Update: This task checks if an account’s LDC has been updated with another one. System checks ESG extract: Datamart_LDC and updates Ops Admin table Addresses with the latest LDC for an account.

  • Dates Update: Contract Dates, Service Dates from Ops Admin are updated with dates information from ESG extract Datamart_Accounts.

  • Plans Information Update: System uses Datamart_Accounts extract from ESG to update an Ops Admin account with its latest plan info. To achieve this, System uses Distributor Name, ESG Plan Code, Commodity, Rate and Monthly Fee to filter Ops Admin Plan’s tables and find the exact plan that the account has. Also, Contract Dates are used to determine the plan’s term.

  • Enrollment Substatus Update: This task updates each account from Ops Admin with its latest substatus from Datamart_Accounts ESG Daily Extract.

  • Phone Numbers: Datamart_Customers extract is used to update Ops Admin Customer’s phone numbers (Service Phone Number and Cellular Phone Number)

 

Relay File Export​

This task is in charge generating the Relay File and exporting it to Relay’s FTP. Settings like passwords, paths, keys, etc can be found on OpsAdmin Service Configuration File. Also, the execution hour is customizable. Currently set up to run at 1:00 AM to export all the enrollments generated the day before.

The system creates a backup of the file before uploading it to P2C FTP folder.

Drops Import​

Executed everyday at 06:45 AM. Can be enabled/disabled from the Configuration file. This task imports the daily dropped accounts from the Datamart Market Detail ESG extract. It brings all the dropped accounts from the day before and the 10 previous days accounts that couldn’t get imported the day before.

To be imported, an account must:

  • Have the “Drop Request” value from the Market Detail ESG Extract.

  • Have a value on the Confirmed Drop Date field from Datamart Accounts ESG Extract.

  • Have a plan that exists in Ops Admin.

  • Contract dates are populated.

The service makes several validations to check if the drop has been imported before, if the account ldc has been updated and also validations against ESG Web Service to get the latest info of each account.

If the dropped account doesn’t exist on Ops Admin, the system creates a Legacy Account.

Price Plan Changes File Export​

Executed every day at 06:00 PM. This task generates the Files for Price Plan Updates and Courtesy Plan Updates.

Service uses accounts that have the following statuses:

  • Price Plan Update Pending

  • Courtesy Plan Reassign Pending

It takes every price changed made that day and generates a file with all the information that must be exported to ESG. Column “Exported file” is updated with “Yes” to know that those accounts have been exported.

The export path for each file can be set up from the Configuration file. The Price Plan Updates file uses a text file while the Courtesy plan update uses an Excel File. Extensions and names can be customized too.

The service saves a local copy of each exported file. It also updates each exported record with an “Exported” label so the operator is aware of which record has already been sent to ESG.

System Logs File Export​

This task generates each System Logs file established from the System Logs Manager. This task is scheduled to run every day at 06:15 PM. This time can be customized as well the ESG FTP credentials information, ESG destination file path, among others. A local copy of each file is generated before exporting it. 

This task can be enabled/disabled from the Service Configuration File and it’s executed everyday at 6.30pm.

Sync Enrollment Dates​

This task executes a Stored Procedure saved at the database. This SP is in charge of updating Ops Admin Enrollments table with the accurate dates from ESG Datamart Extract:

  • Requested Start Date

  • Contract Start Date

  • Contract End Date

  • Service End Date

Only Accepted or Dropped enrollments are updated. Values are updated when Ops Admin has empty date values or ESG’s values are different from the ones that Ops Admins has. 

This task can be enabled/disabled from the Service Configuration File and it’s executed every day at 3:20am.

Plan Updates Switch​

This task works with all the enrollments that have the Price Plan Update Accepted or Courtesy Plan Reassign Accepted.

System gets a list of all the enrollments that have these statuses and compares their contract start date with today’s date. If today’s date equals the contract start date, the enrollment is set to Accepted and the previous enrollment is set to Archived.

This task can be enabled/disabled from the Service Configuration File and it’s executed every day at 6.40pm.

Update Plans​

This task is part of the Global Prices Changes functionality. Operators can set plans to be updated on a certain date. This task checks if there are plans that are supposed to be updated on the current date, updates them and sends emails to affiliates.

This task can be enabled/disabled from the Service Configuration File and it’s executed every day at 6.50pm.

Expired Plans​

This task checks the expiration date of each published plan and if it matches the current date, it sets the plan to unpublished. 

This task also notifies the operators through email when a plan has been set to unpublished and another email when the plan is about to expire.

This task can be enabled/disabled from the Service Configuration File and it’s executed every day at 7am.

Export Renewals​

This task is executed every day at 6pm.

System takes all the renewals generated on the current date, inserts them in a file and exports them to ESG. The ESG FTP path can be set on the Service configuration file as well as FTP credentials and also the file format. If the file has been successfully exported, it’s labeled as “Exported” on the system. The service also creates a copy of the exported file that is stored at the server.

This task can be enabled/disabled from the Service Configuration File.

Check Start Date​

This task is executed every day at 6pm, 12pm, 6am and midnight. 

The Services looks for all the Enrollments that have a “Pending” status and checks each of them against ESG Web Service. If ESG provides a valid Service Start Date, the record is updated to “Accepted”. This task also sends email if the autoresponder for this trigger has been set up.

It may set an enrollment to “Cancelled” if the provided Service Start Date by ESG is previous to the Contract Start Date value assigned to this account.

Email Sending​

There are 3 types of emails handled by the system: Immediate priority, Normal and Daily Emails. Ops Admin service takes care of sending each email added to the Email queue based on its Autoresponders and Priority.

Send Due Plan Notification​

The purpose of this task is to send a notification when the customer’s account is about to expire based on the Market configuration for renewal notifications.

Each Market can send up to two renewal notification notices (Check Market Manager to set up these values).

This task gets a list of all the Accounts that have an “Accepted” status. It also checks on the datamart Accounts extract that the account has an “Active” status there.

It also checks the account sub-status. The following sub-status values have the “Send Contract Expiration Notification” setting activated:

  • Flowing

  • Pending Final

  • Pending Flow

  • Pending Enroll Request

  • Pending Enroll Response

  • Pending Normal Accept

Based on the amount of days set for First Notification and Second Notifications, the system takes the Contract End Date for each account and subtracts the amount of days set up for First/Second Notification and compares that date to current date. If both days match, a notification is sent to the customer.

This task is executed every day at 3am.

Check and Update Expired Enrollments​

This task gets a list of all the enrollments that have an Accepted status but also have a Contract End Date which value is previous to current date. These accounts are set to Expired.

This task is executed every day at 2am.

Make Today Switches​

When a renewal is performed, you end up with two accounts: One account with the status “Renewed” and another one with the “Renewal Accepted” status. This task looks for all the “Renewal Accepted” accounts and updates them to “Accepted”, while the previous Enrollment is set to “Archived”. To update the accounts, this task uses a field called “Renewal Date” which generally matches the Contract Start Date of the Renewal Accepted account.

This task is executed every day at 1am.

Calculate End Dates​

This task takes all the accounts that have an “Accepted” status and no contract end date because they have just been set to Accepted by the system.

This task calculates the Contract End Date based on the Contract Start Date and the plan’s term.